docs: add remote MCP server section to MCP guide#1698
Conversation
Deploying logfire-docs with
|
| Latest commit: |
28009b2
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d4c4c259.logfire-docs.pages.dev |
| Branch Preview URL: | https://hramezani-add-remote-mcp-doc.logfire-docs.pages.dev |
hramezani
force-pushed
the
hramezani/add-remote-mcp-docs
branch
from
d017f92 to
66ef570
Compare
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Add documentation for the hosted remote MCP server as the recommended way to use Logfire MCP. This provides an easier setup experience for users who don't need to run the server locally. - Add Remote MCP Server section at the top with US and EU configs - Reorganize local setup under "Running Locally" section - Keep existing client-specific configurations for local usage Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
hramezani
force-pushed
the
hramezani/add-remote-mcp-docs
branch
from
66ef570 to
0e0a31e
Compare
| ## Running Locally (Deprecated) | ||
|
|
||
| !!! warning | ||
| Running the MCP server locally is deprecated. Please use the [Remote MCP Server](#remote-mcp-server-recommended) instead. | ||
| The local server will continue to work, but we recommend migrating to the remote server for a better experience. | ||
|
|
||
| If you prefer to run the MCP server locally (for example, for self-hosted Logfire or custom configurations), | ||
| you can use the [`logfire-mcp`](https://pypi.org/project/logfire-mcp/) package instead. |
There was a problem hiding this comment.
🚩 Labeling local MCP server as "Deprecated" may be premature for self-hosted users
The section heading ## Running Locally (Deprecated) and the warning admonition at docs/how-to-guides/mcp-server.md:62-64 label the local setup as deprecated. However, the note at docs/how-to-guides/mcp-server.md:55-56 explicitly directs self-hosted Logfire users to this section. Calling a feature "deprecated" while simultaneously recommending it for a valid use case could confuse users — they may think they're using an unsupported path. Consider whether "Alternative" or "Advanced" would be more accurate than "Deprecated" for the heading, or clarify that the deprecation only applies to users who have access to the hosted service.
Was this helpful? React with 👍 or 👎 to provide feedback.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Self-hosted customers have the MCP server in their own deployment, so they should use their instance URL rather than running locally. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
hramezani
force-pushed
the
hramezani/add-remote-mcp-docs
branch
from
d135d10 to
49e735d
Compare
| <div class="video-wrapper"> | ||
| <iframe width="560" height="315" src="https://www.youtube.com/embed/z56NOvrtG74" frameborder="0" allowfullscreen></iframe> | ||
| </div> | ||
|
|
| ## Remote MCP Server (Recommended) | ||
|
|
||
| Pydantic Logfire provides a hosted remote MCP server that you can use without installing anything locally. | ||
| This is the easiest way to get started with the Logfire MCP server. | ||
|
|
||
| To use the remote MCP server, add the following configuration to your MCP client. | ||
|
|
||
| **Choose the endpoint that matches your Logfire data region:** | ||
|
|
||
| For **US region** (`logfire-us.pydantic.dev`): | ||
|
|
||
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "logfire": { | ||
| "type": "http", | ||
| "url": "https://logfire-us.pydantic.dev/mcp" | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| For **EU region** (`logfire-eu.pydantic.dev`): | ||
|
|
||
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "logfire": { | ||
| "type": "http", | ||
| "url": "https://logfire-eu.pydantic.dev/mcp" | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| !!! note | ||
| The remote MCP server handles authentication automatically through your browser. When you first connect, | ||
| you'll be prompted to authenticate with your Pydantic Logfire account. | ||
|
|
||
| !!! note | ||
| If you are running a self-hosted Logfire instance, replace the URL above with your own Logfire instance URL | ||
| (e.g., `https://logfire.my-company.com/mcp`), as the remote MCP server is hosted alongside your Logfire deployment. | ||
|
|
There was a problem hiding this comment.
🚩 No remote MCP configuration examples for specific clients (Cursor, Claude, etc.)
The new Remote MCP Server section at lines 15-57 provides a generic JSON configuration snippet with "type": "http" and a "url" field. However, the client-specific configuration sections (Cursor at line 94, Claude Desktop at line 117, Claude Code at line 144, Cline at line 154) only show local command/args-based configurations. Users wanting to use the remote server with these specific clients may not know how to adapt the generic config. This isn't a bug, but it could be a documentation gap — particularly for Cursor, which has known limitations (e.g., not supporting the env field as noted at line 110-112) and may or may not support "type": "http" MCP server configs.
Was this helpful? React with 👍 or 👎 to provide feedback.
2 participants
Summary
Related
Why
The remote MCP server is easier to set up and doesn't require users to manage a local process or read tokens. Making it the first option in the docs will help users get started faster.
🤖 Generated with Claude Code